API key configuration and bugfixes#38
Open
ColeDCrawford wants to merge 5 commits intoUCSCLibrary:masterfrom
Open
API key configuration and bugfixes#38ColeDCrawford wants to merge 5 commits intoUCSCLibrary:masterfrom
ColeDCrawford wants to merge 5 commits intoUCSCLibrary:masterfrom
Conversation
Same as hanging PRs UCSCLibrary#27 and UCSCLibrary#37
Add config options so users can configure the API key
Library error handling seems to handle a blank fine
Remove default API key
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Incorporates #37 and #27, and adds basic config options so users can add their own YouTube Data API V3 key via the standard Omeka plugin config. The default key is both insecure and has a maxed out request limit but is left as a default.